Production Context
The Last Night at Tremore Beach (La última noche en Tremor, 2024) is a Spanish psychological thriller mini-series directed by Oriol Paulo for Netflix, with production design by Dídac Bono and art direction by Marc Estrugo. Our screen graphics work was coordinated with Assistant Art Director Adrià Porta.
The series required a fully functional Apple environment — macOS on MacBook, iOS on iPhone — shot live and interactive on set. No playback, no pre-rendered loops. Real systems, real interaction, real performance conditions.
The challenge wasn't designing something new. It was replicating something that already exists, in exhaustive detail, while navigating the legal boundaries of what can and cannot be shown.
The IP Problem with Real Screens
Apple's macOS and iOS are immediately recognizable to global audiences. That familiarity is precisely what makes them useful for realistic drama — a character using a MacBook or iPhone reads as authentic without any explanation.
But authenticity has limits.
The specific script requirements made this clear. In one key sequence, a character needed to search for news articles — content that didn't exist and couldn't be found through any real search engine. Using Safari with Google, Bing, or any live search service was impossible: the results couldn't be controlled, and the fictional content couldn't exist there.
The solution was a fictional search engine — Beagle Finds — built to sit inside a real Safari browser. The visual language of the search interface, the results architecture, the typography and layout all needed to feel like a plausible search product. Close enough that no viewer would question it. Different enough that no real service was implicated.
In a second sequence, a character needed to download and read a script sent by email — a scripted interaction requiring precise control over every element visible on screen: sender identity, subject line, attachment behavior, the document itself.
Both sequences required fictional content within a believable Apple environment. Building that content required building the environment around it.
What Replicating macOS Actually Means
Building a fictional Apple-like environment isn't a matter of copying visual style. Apple's interfaces are defined by their behavior — the specific timing of system animations, the micro-interactions that accompany navigation, the way elements respond to input.
Audiences who use these systems daily have internalized those behaviors. An animation that's slightly off-tempo, a transition that doesn't match system conventions, a menu that responds differently than expected — each of these registers subconsciously as wrong, even if viewers couldn't identify exactly why.
We replicated both macOS and iOS to a level of detail that included system-accurate navigation animations and transition timing, a custom-built fictional browser with realistic Safari-like behavior, a fictional search engine with plausible results architecture, a custom Mail environment with scripted inbox, sender logic, and attachment behavior, fictional apps populating the dock and home screens with coherent icon design, and system-level details across menu bar, status indicators, and notification behavior.
The goal wasn't to fool anyone into thinking they were watching real Apple software. It was to ensure that viewers familiar with these systems would never be pulled out of the scene by something that felt technically wrong.
Interactive vs. Playback: A Decision with Consequences
The production initially considered a hybrid approach for the browser sequence: record real macOS navigation for the non-fictional portions, play it back during filming, then replace only the scripted fictional section with interactive content.
We proposed a different approach. Build both sequences as fully interactive systems and remove playback from the equation entirely.
The reason is straightforward: playback constrains performance.
When an actor navigates a playback loop, they're synchronizing their physical actions to pre-recorded movement. Every keystroke, every scroll, every pause has to hit a specific beat. The cognitive load of maintaining that synchronization — even when it becomes second nature — is attention that isn't going to the scene.
Interactive systems change the actor's relationship to the screen entirely. The computer responds to them. They aren't performing alongside a recording; they're operating a tool. Their attention can go to intention, to the other characters in the scene, to what the script actually requires emotionally.
The production chose full interactive. Both the browser sequence and the email sequence ran as live, responsive systems throughout filming. No synchronization required.
iOS: Missed Calls and the Weight of Unanswered Things
Not all the screen work in the production lived on the MacBook. The iOS environment — the iPhone — carried its own set of narrative requirements, and its own design discipline.
One sequence required a lock screen accumulating missed calls from Paula — a name that carries emotional weight in the story. Four notifications, stacked. The kind of screen you look at and immediately understand something about a person's life without needing any dialogue to explain it.
Designing this meant replicating every detail of the iOS lock screen notification stack — the typography, the spacing, the WhatsApp green, the way notifications compress and layer as they accumulate. The fictional content is stark. The design has to be invisible.
The Green Screen Question
One sequence took a different approach, and it's useful to examine what that involves technically.
A mobile phone sequence involving a music player was filmed against green screen. The reasoning was production-practical: the final music choice hadn't been confirmed at the time of shooting, so the decision was made to replace the phone display entirely in post-production.
The technical challenge this creates is straightforward. When an actor interacts with a featureless green surface, there's no tactile reference for where interface elements are. Touches land where instinct places them. In post-production, the designed interface then needs to be adapted to match what the actor's hands actually did — which requires careful tracking and compositing work that interactive on-set systems eliminate entirely.
An alternative approach — green screening only the album artwork while keeping the surrounding interface interactive — would have confined the post-production work to a small, defined area of the frame. Both approaches are valid depending on production priorities. The tradeoff is between flexibility at the time of shooting and additional work downstream.
There's also a budget consideration worth understanding. Green screening a screen element moves cost from the art department to post-production. From a departmental perspective this can look like a saving. At the level of overall production budget, the arithmetic is rarely that simple.
Working at Production Speed
One practical reality of contemporary Spanish production deserves mention, because it shapes everything about how we work.
Pre-production timelines have compressed significantly. Where a production might previously have engaged screen graphics suppliers four to six weeks before shooting began, it's now common to be contacted two to four weeks out — sometimes less. On The Last Night at Tremore Beach, the full Apple environment replication — both macOS and iOS, built interactively to system-animation accuracy — was completed within a tight pre-production window.
Speed without quality loss requires a specific approach. We prioritize the elements that will actually be seen — the sequences identified in the script that require screen interaction — and build those to full fidelity. Background screens, peripheral monitors, and elements that appear at distance receive appropriate attention without consuming the time budget that hero screens require.
The ability to work quickly, deploy remotely, and iterate between office and set is now a baseline capability rather than a differentiator. Productions expect it. Our job is to make that speed invisible.
A Different Kind of Screen: Broadcast Graphics
Not all screen work on Tremor was interactive. One sequence required a different discipline entirely: post-production compositing of a fictional television broadcast.
The shot establishes the protagonist's backstory in a single camera move — a television showing a BAFTA awards ceremony red carpet, panning across boxes of trophies and awards, ending on the character's face watching the screen. The entire exposition of who this person was, and what they've left behind, happens in one continuous plane.
For that television image to carry the weight the shot required, it needed to look like a real broadcast — not a placeholder. We designed the full graphic package: lower thirds with name and award category, channel bug, the visual language of a live awards ceremony transmission. A few seconds of screen time, built to the standard of a complete broadcast identity.
The difference between this work and the interactive macOS environment isn't just technical — it's conceptual. Interactive screens exist in the story space as objects characters use. Composited broadcast graphics exist in the story space as the world beyond the frame — the media environment the character inhabits. Both require the same commitment to plausibility. The tools and the workflow are entirely different.